home *** CD-ROM | disk | FTP | other *** search
- Path: druid.borland.com!usenet
- From: pete@borland.com (Pete Becker)
- Newsgroups: comp.lang.c++
- Subject: Re: Problems with BC50
- Date: 26 Mar 1996 16:29:20 GMT
- Organization: Borland International
- Message-ID: <4j9610$74n@druid.borland.com>
- References: <4j4b8f$7u9@news.interpath.net> <4j633o$3sd@natasha.rmii.com>
- NNTP-Posting-Host: pbecker.borland.com
- Mime-Version: 1.0
- Content-Type: Text/Plain; charset=ISO-8859-1
- X-Newsreader: WinVN 0.99.5
-
- In article <4j633o$3sd@natasha.rmii.com>, gregrice@sylvansoft.com says...
- >
- >In article <4j4b8f$7u9@news.interpath.net>, galaxy@interpath.com (ozone) says:
- >
- >
- >We have been having very similar problems with v5.0. Also, we
- >are unable to recompile existing 4.52 programs in Win 3.1 mode without
- >the linker running out of memory. If anyone knows how to fix that
- >we would sure be interested.
-
- Here's an excerpt from the readme file:
-
- o) Building 16-Bit Applications in Windows 95
- ---------------------------------------------
- When you build 16-bit applications in the IDE, a process called
- CapDos32 remains in memory. If you view PVIEW.EXE, it shows
- these processes as WINOLDAP.
-
- To make these processes unload themselves after 16-bit builds,
- select \WINDOWS\SYSTEM\CONAGENT.EXE, select File | Properties, and
- check Close on exit on the Program page. To avoid running out of
- memory while linking 16-bit applications, set all memory choices
- to Auto on the Memory page of the CONAGENT.EXE properties.
-
-